Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2077e7b6b78ef9a9766334a2fa3801b7679baa02e0e988aaa4d12ee81a6c7dbc

Tx prefix hash: 63a971e15f228c3bbd589eff471baf6bf79fe60320be22fe75ce67ce3cfd7b0a
Tx public key: 8d3c4ab5ec3a62e1b55b988bc1d7e8b2364dec2073d54ccf0edd92cd69d1ba17
Timestamp: 1709935458 Timestamp [UCT]: 2024-03-08 22:04:18 Age [y:d:h:m:s]: 01:072:00:58:43
Block: 974122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312497 RingCT/type: yes/0
Extra: 018d3c4ab5ec3a62e1b55b988bc1d7e8b2364dec2073d54ccf0edd92cd69d1ba1702110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f56913faff87da9fb8e7b36e6af7fa5ec0a52acddf536f97073fff2f9412f2e8 0.600000000000 1434073 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": 974132, "vin": [ { "gen": { "height": 974122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f56913faff87da9fb8e7b36e6af7fa5ec0a52acddf536f97073fff2f9412f2e8" } } ], "extra": [ 1, 141, 60, 74, 181, 236, 58, 98, 225, 181, 91, 152, 139, 193, 215, 232, 178, 54, 77, 236, 32, 115, 213, 76, 207, 14, 221, 146, 205, 105, 209, 186, 23, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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