Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dbbdbb086e43fa2bd30b7c7c42c8a0a7c8f2a5379fd8c1c98b1f5c0e3949145

Tx prefix hash: 540f4086ebe66dc56a918ed4358a8764e366060f05eceffea39276c3cf2abdb4
Tx public key: 15c393680487079da41c2bc1c6d20beecfadb0c5f3c3be0073072cdc50a23488
Timestamp: 1718741391 Timestamp [UCT]: 2024-06-18 20:09:51 Age [y:d:h:m:s]: 00:307:22:03:03
Block: 1047118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220049 RingCT/type: yes/0
Extra: 0115c393680487079da41c2bc1c6d20beecfadb0c5f3c3be0073072cdc50a234880211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6606eeefbb6195b3a5446346f87de8a90af1bef9d7c9c3ea1d785bc19dc9b9a 0.600000000000 1516937 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": 1047128, "vin": [ { "gen": { "height": 1047118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6606eeefbb6195b3a5446346f87de8a90af1bef9d7c9c3ea1d785bc19dc9b9a" } } ], "extra": [ 1, 21, 195, 147, 104, 4, 135, 7, 157, 164, 28, 43, 193, 198, 210, 11, 238, 207, 173, 176, 197, 243, 195, 190, 0, 115, 7, 44, 220, 80, 162, 52, 136, 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