Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee507823acb9318c1eb8995c700e46ba70af972881f6716370486bad0057096

Tx prefix hash: 1f0c7e4c1b9c3cee54d1f44ec22d63bc3e6142c8e7df66f8e1a690b1a39b7334
Tx public key: a122e5f453f8501ddb8a799d598f04d2a79a1f13ce5c2b9d763c3b435a547867
Timestamp: 1709971993 Timestamp [UCT]: 2024-03-09 08:13:13 Age [y:d:h:m:s]: 01:245:02:44:28
Block: 974429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433892 RingCT/type: yes/0
Extra: 01a122e5f453f8501ddb8a799d598f04d2a79a1f13ce5c2b9d763c3b435a54786702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ff5011bb8b795761f9b172b1429445ff0780c61c654e024586dc0282977f8a 0.600000000000 1434384 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": 974439, "vin": [ { "gen": { "height": 974429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ff5011bb8b795761f9b172b1429445ff0780c61c654e024586dc0282977f8a" } } ], "extra": [ 1, 161, 34, 229, 244, 83, 248, 80, 29, 219, 138, 121, 157, 89, 143, 4, 210, 167, 154, 31, 19, 206, 92, 43, 157, 118, 60, 59, 67, 90, 84, 120, 103, 2, 17, 0, 0, 0, 1, 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