Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 248e762d48b2ecdea71666f86e1a69326dba4d1cc3a9028618e7a8c385151e74

Tx prefix hash: 6c903dcbecb56f876063c394a6f421e102e8abbd7572fa98f0cb146e0ba38e78
Tx public key: 58b9d9fb35b11c90dbf034431204a163e7d8179978cfcbfc5527ed324b15573b
Timestamp: 1724883610 Timestamp [UCT]: 2024-08-28 22:20:10 Age [y:d:h:m:s]: 00:248:10:34:21
Block: 1098037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177434 RingCT/type: yes/0
Extra: 0158b9d9fb35b11c90dbf034431204a163e7d8179978cfcbfc5527ed324b15573b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 133810d62e0e1aef4f37f0b3b0b4ab144bba8e2d18e01334e4f0ce7cac807d45 0.600000000000 1573616 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1098047, "vin": [ { "gen": { "height": 1098037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "133810d62e0e1aef4f37f0b3b0b4ab144bba8e2d18e01334e4f0ce7cac807d45" } } ], "extra": [ 1, 88, 185, 217, 251, 53, 177, 28, 144, 219, 240, 52, 67, 18, 4, 161, 99, 231, 216, 23, 153, 120, 207, 203, 252, 85, 39, 237, 50, 75, 21, 87, 59, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8