Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8844a9a4a5fad0978afc644ecb9dde512f6405728052cd7b4aba5b417414fe60

Tx prefix hash: baf3bce53c84308d626a1be248352365663e1fcdba9c929819fb7ab16acbf0e8
Tx public key: 4277eb8d2a615807c4c3407dccb1c5aef5f892161163365fb05f63cbd1619a2a
Timestamp: 1743836631 Timestamp [UCT]: 2025-04-05 07:03:51 Age [y:d:h:m:s]: 00:230:07:59:35
Block: 1254679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162341 RingCT/type: yes/0
Extra: 014277eb8d2a615807c4c3407dccb1c5aef5f892161163365fb05f63cbd1619a2a0211000000084060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69bfc5d95f37ed891ad5964a4b43d352e5507e53908ca827c88037cb7f31df4d 0.600000000000 1741760 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": 1254689, "vin": [ { "gen": { "height": 1254679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69bfc5d95f37ed891ad5964a4b43d352e5507e53908ca827c88037cb7f31df4d" } } ], "extra": [ 1, 66, 119, 235, 141, 42, 97, 88, 7, 196, 195, 64, 125, 204, 177, 197, 174, 245, 248, 146, 22, 17, 99, 54, 95, 176, 95, 99, 203, 209, 97, 154, 42, 2, 17, 0, 0, 0, 8, 64, 96, 246, 210, 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