Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8cf8edc0782ad94869ae7b5b4c87648f8575197a701537ddabb72550ee08f96

Tx prefix hash: 7333518b1c0f9ec1f053e7666dba3a1740b6a5ca919715ea4f66e61e0e68541b
Tx public key: 6d92c469f94dfc4fcb1cc98a433a327bc4f5402c2da2d7ce1c3adc956e7f0c36
Timestamp: 1674280348 Timestamp [UCT]: 2023-01-21 05:52:28 Age [y:d:h:m:s]: 01:291:02:51:37
Block: 679381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469032 RingCT/type: yes/0
Extra: 016d92c469f94dfc4fcb1cc98a433a327bc4f5402c2da2d7ce1c3adc956e7f0c360211000000045029cbac000000000000000000

1 output(s) for total of 3.442933751000 dcy

stealth address amount amount idx
00: 4c7fb51cd2805d2b57e4cc1f0e6d50c7f17c258088fce10cb5421ef379f7897e 3.442933751000 1121358 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": 679391, "vin": [ { "gen": { "height": 679381 } } ], "vout": [ { "amount": 3442933751, "target": { "key": "4c7fb51cd2805d2b57e4cc1f0e6d50c7f17c258088fce10cb5421ef379f7897e" } } ], "extra": [ 1, 109, 146, 196, 105, 249, 77, 252, 79, 203, 28, 201, 138, 67, 58, 50, 123, 196, 245, 64, 44, 45, 162, 215, 206, 28, 58, 220, 149, 110, 127, 12, 54, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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