Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 381560d1331f7f2f0d41402fef74c8120dd031ebcafc92cb2ed8021a32e92c65

Tx prefix hash: 0cf30b83cc756a1396ec5928811b2a4dcb05649e8ddf52d68a9a406752e21bc9
Tx public key: 949ff44c8d47f1093897e5b15535ac4807048fd9fdd92e5bae9d69306c1e1596
Timestamp: 1686074504 Timestamp [UCT]: 2023-06-06 18:01:44 Age [y:d:h:m:s]: 01:344:20:20:31
Block: 776543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507682 RingCT/type: yes/0
Extra: 01949ff44c8d47f1093897e5b15535ac4807048fd9fdd92e5bae9d69306c1e159602110000000675e3f0e9000000000000000000

1 output(s) for total of 1.640555197000 dcy

stealth address amount amount idx
00: b90fded263d63a1983a2a19c334b5cf9c23ff027a01e7688a5ca03b0e58dfa58 1.640555197000 1226098 of 0

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": 776553, "vin": [ { "gen": { "height": 776543 } } ], "vout": [ { "amount": 1640555197, "target": { "key": "b90fded263d63a1983a2a19c334b5cf9c23ff027a01e7688a5ca03b0e58dfa58" } } ], "extra": [ 1, 148, 159, 244, 76, 141, 71, 241, 9, 56, 151, 229, 177, 85, 53, 172, 72, 7, 4, 143, 217, 253, 217, 46, 91, 174, 157, 105, 48, 108, 30, 21, 150, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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