Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e270b346cd2d0319a9bf1ddd720db097178f4d3208c322c59aabbd8e24389c39

Tx prefix hash: 48d609434f289e034e2e8232baa4dda9de59e10acf4a21850a3169e49013fc1c
Tx public key: 79388d9c642d8d7f7f17a3fb2e54f64bdc0249fbf0071f6dcdff698bc6391da2
Timestamp: 1711423608 Timestamp [UCT]: 2024-03-26 03:26:48 Age [y:d:h:m:s]: 01:086:18:54:17
Block: 986479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322859 RingCT/type: yes/0
Extra: 0179388d9c642d8d7f7f17a3fb2e54f64bdc0249fbf0071f6dcdff698bc6391da202110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ace5b10fd9ded3e0bfe4040975e39a643fc5a63e09afcc3bd96fbffe28b96612 0.600000000000 1446708 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": 986489, "vin": [ { "gen": { "height": 986479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ace5b10fd9ded3e0bfe4040975e39a643fc5a63e09afcc3bd96fbffe28b96612" } } ], "extra": [ 1, 121, 56, 141, 156, 100, 45, 141, 127, 127, 23, 163, 251, 46, 84, 246, 75, 220, 2, 73, 251, 240, 7, 31, 109, 205, 255, 105, 139, 198, 57, 29, 162, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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