Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a48d0f97d19a24d825066fb8aa1200e7f4abbaf4e2cc304e925ae20eedfa4fb5

Tx prefix hash: 6c1c5e255ce1df2fd468f5785742e7b73acc08d87d2bd095f5952b0e244db830
Tx public key: ac2a8c3f54010afb39881422d15ee1c95cde93806667820703dc1aad028f90e6
Timestamp: 1706466009 Timestamp [UCT]: 2024-01-28 18:20:09 Age [y:d:h:m:s]: 01:067:23:38:53
Block: 945330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309674 RingCT/type: yes/0
Extra: 01ac2a8c3f54010afb39881422d15ee1c95cde93806667820703dc1aad028f90e602110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55e0bb337cc1cdd385153a24e7a38b367430044ae97574b6634c730b44eaf526 0.600000000000 1403642 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": 945340, "vin": [ { "gen": { "height": 945330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55e0bb337cc1cdd385153a24e7a38b367430044ae97574b6634c730b44eaf526" } } ], "extra": [ 1, 172, 42, 140, 63, 84, 1, 10, 251, 57, 136, 20, 34, 209, 94, 225, 201, 92, 222, 147, 128, 102, 103, 130, 7, 3, 220, 26, 173, 2, 143, 144, 230, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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