Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47116ebccb1caec6137078f4ba92397c192ce8ff69a4d95cbf49f39994d73315

Tx prefix hash: 7d58c3001e588bcc2fdf960164388ac5a365b58324ddfbe6e985438d3c1b0116
Tx public key: e42f950b4ba01dc2c4382df0a8ac926351495e8f6bfc9d394e908d4cbb1bbd33
Timestamp: 1738503201 Timestamp [UCT]: 2025-02-02 13:33:21 Age [y:d:h:m:s]: 00:290:00:35:12
Block: 1210521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205050 RingCT/type: yes/0
Extra: 01e42f950b4ba01dc2c4382df0a8ac926351495e8f6bfc9d394e908d4cbb1bbd330211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc73e3545b0b6f31f839979b4ae7336c82bf8df4166f179bfd72b65eb38982cb 0.600000000000 1697274 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": 1210531, "vin": [ { "gen": { "height": 1210521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc73e3545b0b6f31f839979b4ae7336c82bf8df4166f179bfd72b65eb38982cb" } } ], "extra": [ 1, 228, 47, 149, 11, 75, 160, 29, 194, 196, 56, 45, 240, 168, 172, 146, 99, 81, 73, 94, 143, 107, 252, 157, 57, 78, 144, 141, 76, 187, 27, 189, 51, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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