Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36881be510da171136598db6f62953eb3520424ef58a4541fad2ce43bf9bbf84

Tx prefix hash: 29825344fcc60de8b6c6394b7ed436a85fbbd7f50a8d4e16d6a9c239ff0d6b6d
Tx public key: d2923c4888f093750f15449fe8809aa4fab4b562f0111ac81086b5876c8e341f
Timestamp: 1749138028 Timestamp [UCT]: 2025-06-05 15:40:28 Age [y:d:h:m:s]: 00:157:09:00:46
Block: 1298586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110144 RingCT/type: yes/0
Extra: 01d2923c4888f093750f15449fe8809aa4fab4b562f0111ac81086b5876c8e341f021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5124735c1da6cc3ae0054ee6e3cbaba7d28a7b1743251350831b18a64a17fe0d 0.600000000000 1786115 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": 1298596, "vin": [ { "gen": { "height": 1298586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5124735c1da6cc3ae0054ee6e3cbaba7d28a7b1743251350831b18a64a17fe0d" } } ], "extra": [ 1, 210, 146, 60, 72, 136, 240, 147, 117, 15, 21, 68, 159, 232, 128, 154, 164, 250, 180, 181, 98, 240, 17, 26, 200, 16, 134, 181, 135, 108, 142, 52, 31, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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