Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecc321f58afab05e22dd51909dd1220911993c766041d2449d4bf99510c456bd

Tx prefix hash: 0c9df95e272795015a603d1e131268f050726e4a570bc606e1f9ef76088f83ea
Tx public key: ea9ebb60c3dbce1ad74c1f8b7ac38a96c78a4530122a8a4a88fc0ba8aca3ab9f
Timestamp: 1711658366 Timestamp [UCT]: 2024-03-28 20:39:26 Age [y:d:h:m:s]: 01:226:01:25:01
Block: 988416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420241 RingCT/type: yes/0
Extra: 01ea9ebb60c3dbce1ad74c1f8b7ac38a96c78a4530122a8a4a88fc0ba8aca3ab9f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e6eea1b841ce809e827079c6f61715ea4c0f99cdbc0d0076a32265bff64114f 0.600000000000 1448695 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": 988426, "vin": [ { "gen": { "height": 988416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e6eea1b841ce809e827079c6f61715ea4c0f99cdbc0d0076a32265bff64114f" } } ], "extra": [ 1, 234, 158, 187, 96, 195, 219, 206, 26, 215, 76, 31, 139, 122, 195, 138, 150, 199, 138, 69, 48, 18, 42, 138, 74, 136, 252, 11, 168, 172, 163, 171, 159, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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