Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737ca54b9e8ec92a64f9df00229991991c669f55232ce266354a45438fdfbd82

Tx prefix hash: 7a9f8749020fcf953ee5513bb8205429473ae4ababd89e380296b47948a35c25
Tx public key: 13164efc9cdf81a22b171d2cfb14b4fb4aa1b9f9cf170792abdaa108d7b40f9c
Timestamp: 1722984405 Timestamp [UCT]: 2024-08-06 22:46:45 Age [y:d:h:m:s]: 00:077:12:37:23
Block: 1082290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55510 RingCT/type: yes/0
Extra: 0113164efc9cdf81a22b171d2cfb14b4fb4aa1b9f9cf170792abdaa108d7b40f9c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9673df635e67eac65033f5b0ea3db470b2147e1c2e29895b97bfe28fffd12b9e 0.600000000000 1556115 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": 1082300, "vin": [ { "gen": { "height": 1082290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9673df635e67eac65033f5b0ea3db470b2147e1c2e29895b97bfe28fffd12b9e" } } ], "extra": [ 1, 19, 22, 78, 252, 156, 223, 129, 162, 43, 23, 29, 44, 251, 20, 180, 251, 74, 161, 185, 249, 207, 23, 7, 146, 171, 218, 161, 8, 215, 180, 15, 156, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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