Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60fd4071b877ccbaf6adc549d46b953c1577a766c81f5eece3a3cb9066cf405d

Tx prefix hash: ddb1cf429df8f5da4863ade2c88f32be0d76812df8faaa0c05d4d958108fbe29
Tx public key: fb4def36374ba5e85365a3f019fa5cc210f79615ddb40b98d281396aea5fe10a
Timestamp: 1714438547 Timestamp [UCT]: 2024-04-30 00:55:47 Age [y:d:h:m:s]: 00:255:04:29:27
Block: 1011442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182659 RingCT/type: yes/0
Extra: 01fb4def36374ba5e85365a3f019fa5cc210f79615ddb40b98d281396aea5fe10a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96dc0a060b76c4eb24510c8670825aa4f438288ab99e2046518fe7d603a4daa9 0.600000000000 1473676 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": 1011452, "vin": [ { "gen": { "height": 1011442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96dc0a060b76c4eb24510c8670825aa4f438288ab99e2046518fe7d603a4daa9" } } ], "extra": [ 1, 251, 77, 239, 54, 55, 75, 165, 232, 83, 101, 163, 240, 25, 250, 92, 194, 16, 247, 150, 21, 221, 180, 11, 152, 210, 129, 57, 106, 234, 95, 225, 10, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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