Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33bbf1b8beeb71872518ec53b2fbb508abec66acbb35272494a5b6d7bcb6394

Tx prefix hash: 4426c817a3c668b10844b431e027abccb9670ef6a4c050b3847a95ecb4fdeba1
Tx public key: cc3a75305a69bae40207e811e76d8ecdd79f9121058016f7e20f600147e3f6e7
Timestamp: 1751767566 Timestamp [UCT]: 2025-07-06 02:06:06 Age [y:d:h:m:s]: 00:135:07:12:16
Block: 1319628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95086 RingCT/type: yes/0
Extra: 01cc3a75305a69bae40207e811e76d8ecdd79f9121058016f7e20f600147e3f6e702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d5d7686303c4647c8e7f57fd4c81aa860e033c05f00363b48e6b9ba34590ea8 0.600000000000 1807321 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": 1319638, "vin": [ { "gen": { "height": 1319628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d5d7686303c4647c8e7f57fd4c81aa860e033c05f00363b48e6b9ba34590ea8" } } ], "extra": [ 1, 204, 58, 117, 48, 90, 105, 186, 228, 2, 7, 232, 17, 231, 109, 142, 205, 215, 159, 145, 33, 5, 128, 22, 247, 226, 15, 96, 1, 71, 227, 246, 231, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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