Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb19becf465ae1f50200072a49fa2fdb4b206abb60d6c8ceb34a60227e9cbcf1

Tx prefix hash: 42676f1ba6881068c8fe6d0c94b6c8007f765a49e41f868af9e3d6e18ef73080
Tx public key: c143eacadaaf95733db37c1424efe9d5e9330d1dc7ed4d5dcd997e3e26bd3f3f
Timestamp: 1757080090 Timestamp [UCT]: 2025-09-05 13:48:10 Age [y:d:h:m:s]: 00:139:01:35:45
Block: 1361944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99350 RingCT/type: yes/0
Extra: 01c143eacadaaf95733db37c1424efe9d5e9330d1dc7ed4d5dcd997e3e26bd3f3f021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dd083f36ed545baee692a15440bbe4fbf83eebb5edd0a23e3b1864256146577 0.600000000000 1849967 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": 1361954, "vin": [ { "gen": { "height": 1361944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dd083f36ed545baee692a15440bbe4fbf83eebb5edd0a23e3b1864256146577" } } ], "extra": [ 1, 193, 67, 234, 202, 218, 175, 149, 115, 61, 179, 124, 20, 36, 239, 233, 213, 233, 51, 13, 29, 199, 237, 77, 93, 205, 153, 126, 62, 38, 189, 63, 63, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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