Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce182605137ae3f4ea629e8bdf86fa95061c149fc1452a69d7a785d313a6c8eb

Tx prefix hash: 3dc4cf5577d0125d64d505e016b848413085e8ff3b6486e3a28ddfabe96de0e7
Tx public key: 7c29a4f7513b074f59d97ec70b175d4bc923050225b943903fcf268edcaffe0f
Timestamp: 1733880224 Timestamp [UCT]: 2024-12-11 01:23:44 Age [y:d:h:m:s]: 00:107:00:22:59
Block: 1172537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76266 RingCT/type: yes/0
Extra: 017c29a4f7513b074f59d97ec70b175d4bc923050225b943903fcf268edcaffe0f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a14c86ff5e912cdcf9ad57eb04e190e6347a5e376c680727f5701a6f2ed4d2b 0.600000000000 1658442 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": 1172547, "vin": [ { "gen": { "height": 1172537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a14c86ff5e912cdcf9ad57eb04e190e6347a5e376c680727f5701a6f2ed4d2b" } } ], "extra": [ 1, 124, 41, 164, 247, 81, 59, 7, 79, 89, 217, 126, 199, 11, 23, 93, 75, 201, 35, 5, 2, 37, 185, 67, 144, 63, 207, 38, 142, 220, 175, 254, 15, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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