Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56897a53cd3c2c36be2d43d2db9abacdd83d190ca045f2430fb8075ebfbfaab5

Tx prefix hash: b4e988af12a3bce322e94e0d60dbe0ddaf98e77374512a28b5d5709587298d9c
Tx public key: 474d8a89c13c552b037a7d45ae531e610f764738ab21498d3383ea8aac25bc36
Timestamp: 1709316648 Timestamp [UCT]: 2024-03-01 18:10:48 Age [y:d:h:m:s]: 01:085:01:00:16
Block: 969002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321814 RingCT/type: yes/0
Extra: 01474d8a89c13c552b037a7d45ae531e610f764738ab21498d3383ea8aac25bc360211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2dde24843180fe7814a65b0b9ac3c641c4785e4aea1ad43432666b5dab28d94 0.600000000000 1428829 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": 969012, "vin": [ { "gen": { "height": 969002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2dde24843180fe7814a65b0b9ac3c641c4785e4aea1ad43432666b5dab28d94" } } ], "extra": [ 1, 71, 77, 138, 137, 193, 60, 85, 43, 3, 122, 125, 69, 174, 83, 30, 97, 15, 118, 71, 56, 171, 33, 73, 141, 51, 131, 234, 138, 172, 37, 188, 54, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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