Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47bd3f48371a1350f6c158dd8ffa5f5fb8f1f5c4f3f19111e37061e14d7fc469

Tx prefix hash: aea4feb8d4bcb9210c6cddd3a3c3c049359dfa69e98dd4ed179e46fcd5d71aab
Tx public key: 08b3b94a63b7f5280832d03621057618db1678db3e9df5669aa8b777db3321c4
Timestamp: 1754484249 Timestamp [UCT]: 2025-08-06 12:44:09 Age [y:d:h:m:s]: 00:102:22:32:57
Block: 1341460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72594 RingCT/type: yes/0
Extra: 0108b3b94a63b7f5280832d03621057618db1678db3e9df5669aa8b777db3321c40211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bf51853a09d9f57a3ded74dc60b755717679d4b8e4c92f6ce9a951294729624 0.600000000000 1829285 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": 1341470, "vin": [ { "gen": { "height": 1341460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bf51853a09d9f57a3ded74dc60b755717679d4b8e4c92f6ce9a951294729624" } } ], "extra": [ 1, 8, 179, 185, 74, 99, 183, 245, 40, 8, 50, 208, 54, 33, 5, 118, 24, 219, 22, 120, 219, 62, 157, 245, 102, 154, 168, 183, 119, 219, 51, 33, 196, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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