Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b716d7d01ffe214e5ac7cb356997ba6008a83273343f416d9f5e820895746cc

Tx prefix hash: 476dae995a05e8842ab7499269bd7bae1b63beef23ff46e9567211f2e9ee3a70
Tx public key: 5f9d1f8afc5cfff2b08b989b92bd6f1a3b27801f2c4372eb085b9f640195f612
Timestamp: 1733912493 Timestamp [UCT]: 2024-12-11 10:21:33 Age [y:d:h:m:s]: 00:098:06:54:45
Block: 1172805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70038 RingCT/type: yes/0
Extra: 015f9d1f8afc5cfff2b08b989b92bd6f1a3b27801f2c4372eb085b9f640195f6120211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51a29cebaaef0514caab344aca064ca24b4d972d01135fbee71a54b7eb437e81 0.600000000000 1658742 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": 1172815, "vin": [ { "gen": { "height": 1172805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51a29cebaaef0514caab344aca064ca24b4d972d01135fbee71a54b7eb437e81" } } ], "extra": [ 1, 95, 157, 31, 138, 252, 92, 255, 242, 176, 139, 152, 155, 146, 189, 111, 26, 59, 39, 128, 31, 44, 67, 114, 235, 8, 91, 159, 100, 1, 149, 246, 18, 2, 17, 0, 0, 0, 4, 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