Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49840a00129df43eef948482fcae2f7661871888da119cc9f723cc4a55fca692

Tx prefix hash: 6d7dd6b1b4b39cbe45ee8c9ef9a38699e839cd439431088413011c97a16de577
Tx public key: d259c91a7bfa62a7d0a96aa6e4bdbf4cd8485819fe2e5239fa63d32866b8fbdb
Timestamp: 1747114573 Timestamp [UCT]: 2025-05-13 05:36:13 Age [y:d:h:m:s]: 00:147:21:12:31
Block: 1281814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103336 RingCT/type: yes/0
Extra: 01d259c91a7bfa62a7d0a96aa6e4bdbf4cd8485819fe2e5239fa63d32866b8fbdb0211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 006f6971f73933082e1c3c38ebb0b0aad86d92005e5cc31b505a15c0d4bcd365 0.600000000000 1769217 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": 1281824, "vin": [ { "gen": { "height": 1281814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "006f6971f73933082e1c3c38ebb0b0aad86d92005e5cc31b505a15c0d4bcd365" } } ], "extra": [ 1, 210, 89, 201, 26, 123, 250, 98, 167, 208, 169, 106, 166, 228, 189, 191, 76, 216, 72, 88, 25, 254, 46, 82, 57, 250, 99, 211, 40, 102, 184, 251, 219, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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