Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d574f31880227a2489d741265b6e7ff22c23733c7704ab2f818fd4c0201394a6

Tx prefix hash: 6d9d051193ab29534267f2e6ab77090e5a29227b5ad3bddd4d1dcb6909ffc41a
Tx public key: 5841ea1aa53a71fd9ff2c26bc60cbf89e29cfb5ba161c98705358c900049db45
Timestamp: 1574711488 Timestamp [UCT]: 2019-11-25 19:51:28 Age [y:d:h:m:s]: 05:100:10:28:03
Block: 17376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214385 RingCT/type: yes/0
Extra: 015841ea1aa53a71fd9ff2c26bc60cbf89e29cfb5ba161c98705358c900049db4502110000001f354bbe3b000000000000000000

1 output(s) for total of 537.590222440000 dcy

stealth address amount amount idx
00: 34b18aa1ce9463dd0fa58336ff14b4c14bcc94a85871dc91e8bc1f9445327c82 537.590222440000 25183 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": 17386, "vin": [ { "gen": { "height": 17376 } } ], "vout": [ { "amount": 537590222440, "target": { "key": "34b18aa1ce9463dd0fa58336ff14b4c14bcc94a85871dc91e8bc1f9445327c82" } } ], "extra": [ 1, 88, 65, 234, 26, 165, 58, 113, 253, 159, 242, 194, 107, 198, 12, 191, 137, 226, 156, 251, 91, 161, 97, 201, 135, 5, 53, 140, 144, 0, 73, 219, 69, 2, 17, 0, 0, 0, 31, 53, 75, 190, 59, 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