Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bae1e069a5be4564081cf4165b9adb3aa9e32e024f6d7290936649192bf3af83

Tx prefix hash: b8c016b3cc4cbf89991ddc342936edebf7be90b152f432fc1ea7d73b24be8bbd
Tx public key: 8fa6ff76794d44acb9a89faf608b783847c73435daea591f76ef862d48d2a52c
Timestamp: 1715019604 Timestamp [UCT]: 2024-05-06 18:20:04 Age [y:d:h:m:s]: 01:186:04:16:17
Block: 1016275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391673 RingCT/type: yes/0
Extra: 018fa6ff76794d44acb9a89faf608b783847c73435daea591f76ef862d48d2a52c0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35c922eaf64be77f3d573d85a8289a7a2d1e211734c917f0a1f755a69db0f91e 0.600000000000 1479810 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": 1016285, "vin": [ { "gen": { "height": 1016275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35c922eaf64be77f3d573d85a8289a7a2d1e211734c917f0a1f755a69db0f91e" } } ], "extra": [ 1, 143, 166, 255, 118, 121, 77, 68, 172, 185, 168, 159, 175, 96, 139, 120, 56, 71, 199, 52, 53, 218, 234, 89, 31, 118, 239, 134, 45, 72, 210, 165, 44, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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