Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503d61d25045167dab04d8c201982ab7f009bdd4f5c2ddfa52c208fb30a14f54

Tx prefix hash: 27941dc5f2131bed1e2e517e5730435828b0570faa22d4c176abcf3fc03be81e
Tx public key: 7f6362b77df4f278a4c87b06cf731549bce54a5df2a734590d7eb47d7036fad7
Timestamp: 1661227417 Timestamp [UCT]: 2022-08-23 04:03:37 Age [y:d:h:m:s]: 02:084:18:18:15
Block: 571843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581982 RingCT/type: yes/0
Extra: 017f6362b77df4f278a4c87b06cf731549bce54a5df2a734590d7eb47d7036fad7021100000008e6d27f9c000000000000000000

1 output(s) for total of 7.820722171000 dcy

stealth address amount amount idx
00: a7937d8b88c10fb5d1ca6a5d8053b4eff489ca1967a19eea9a947c2ab574e967 7.820722171000 1005071 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": 571853, "vin": [ { "gen": { "height": 571843 } } ], "vout": [ { "amount": 7820722171, "target": { "key": "a7937d8b88c10fb5d1ca6a5d8053b4eff489ca1967a19eea9a947c2ab574e967" } } ], "extra": [ 1, 127, 99, 98, 183, 125, 244, 242, 120, 164, 200, 123, 6, 207, 115, 21, 73, 188, 229, 74, 93, 242, 167, 52, 89, 13, 126, 180, 125, 112, 54, 250, 215, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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