Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d330e2340194f26d7f306cb8c756e61387e0ad8b435568cea8382d45527b089f

Tx prefix hash: 2fd664e2a9dfe06c1f7a6a79c7bdab95bf31ea36f2afbe7a8ac910d551642b60
Tx public key: 2e1c83245063c6d3d43609529beb114d48c695ad38e92da0a085f4ecf2dc6618
Timestamp: 1736840030 Timestamp [UCT]: 2025-01-14 07:33:50 Age [y:d:h:m:s]: 00:155:05:00:23
Block: 1197022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110635 RingCT/type: yes/0
Extra: 012e1c83245063c6d3d43609529beb114d48c695ad38e92da0a085f4ecf2dc6618021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9c557a375ece6e9231409ef04005e19b94535907c4a0f6bc3a7f400ca4cb022 0.600000000000 1683627 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": 1197032, "vin": [ { "gen": { "height": 1197022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9c557a375ece6e9231409ef04005e19b94535907c4a0f6bc3a7f400ca4cb022" } } ], "extra": [ 1, 46, 28, 131, 36, 80, 99, 198, 211, 212, 54, 9, 82, 155, 235, 17, 77, 72, 198, 149, 173, 56, 233, 45, 160, 160, 133, 244, 236, 242, 220, 102, 24, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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