Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad702843f61385fbcab4174a2cd4f75c08ffdec15fca78be7cb33a29fec3fbe2

Tx prefix hash: 33c1c84319f2cfd7b913b4864a7d800bc59f2e1e98121073b0d832d1ddc27c6a
Tx public key: d6d31b9349c5277fcc467c6456637760a0ef13ce40f07e2f8e1dde813f96f112
Timestamp: 1683531527 Timestamp [UCT]: 2023-05-08 07:38:47 Age [y:d:h:m:s]: 02:033:23:57:51
Block: 755469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546440 RingCT/type: yes/0
Extra: 01d6d31b9349c5277fcc467c6456637760a0ef13ce40f07e2f8e1dde813f96f112021100000001e7ace25d000000000000000000

1 output(s) for total of 1.926716373000 dcy

stealth address amount amount idx
00: 327c86cfc5794e2287f2ddb547bc0af2ea2ab2b6ee3034c25a8b736d05a2268b 1.926716373000 1203786 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": 755479, "vin": [ { "gen": { "height": 755469 } } ], "vout": [ { "amount": 1926716373, "target": { "key": "327c86cfc5794e2287f2ddb547bc0af2ea2ab2b6ee3034c25a8b736d05a2268b" } } ], "extra": [ 1, 214, 211, 27, 147, 73, 197, 39, 127, 204, 70, 124, 100, 86, 99, 119, 96, 160, 239, 19, 206, 64, 240, 126, 47, 142, 29, 222, 129, 63, 150, 241, 18, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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