Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484862b764049b9584d3998897095505f56804f7ee526fce624446d588f1b1bd

Tx prefix hash: 2542b713170b4a7489bebe06f09f810ad366b37c28925464a69809dace8e9f86
Tx public key: 19a3333cf3cecd7afd7cd8621b81966f4d183a2e798d41e1d92c7cf5f8aa839b
Timestamp: 1715140238 Timestamp [UCT]: 2024-05-08 03:50:38 Age [y:d:h:m:s]: 01:023:02:57:51
Block: 1017270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277469 RingCT/type: yes/0
Extra: 0119a3333cf3cecd7afd7cd8621b81966f4d183a2e798d41e1d92c7cf5f8aa839b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78d45e947b8d6c80affa29af9475794a9f3192f04be2ea0e345af0a42691fae2 0.600000000000 1481041 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": 1017280, "vin": [ { "gen": { "height": 1017270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78d45e947b8d6c80affa29af9475794a9f3192f04be2ea0e345af0a42691fae2" } } ], "extra": [ 1, 25, 163, 51, 60, 243, 206, 205, 122, 253, 124, 216, 98, 27, 129, 150, 111, 77, 24, 58, 46, 121, 141, 65, 225, 217, 44, 124, 245, 248, 170, 131, 155, 2, 17, 0, 0, 0, 1, 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