Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e3c951d8f3fca27a0f5c174aab8ff11c82320918f0cd21c2d1acdc9c7a4ef76

Tx prefix hash: 98ac11ab23ffdea9c59e63ad756e5937d7e9a8f82a7c63f3ed3bfc2ec51ab8a5
Tx public key: f7d68a2574e94861dcad60a1e8074074a971d642511bd939d8e00282e7f15b6e
Timestamp: 1714100207 Timestamp [UCT]: 2024-04-26 02:56:47 Age [y:d:h:m:s]: 00:273:00:44:16
Block: 1008633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195382 RingCT/type: yes/0
Extra: 01f7d68a2574e94861dcad60a1e8074074a971d642511bd939d8e00282e7f15b6e02110000000439e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d3bc4a86acc775ef6ea4c2bd141a7935e5bcf4de2d4d690508ff557f5763ff4 0.600000000000 1470105 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": 1008643, "vin": [ { "gen": { "height": 1008633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3bc4a86acc775ef6ea4c2bd141a7935e5bcf4de2d4d690508ff557f5763ff4" } } ], "extra": [ 1, 247, 214, 138, 37, 116, 233, 72, 97, 220, 173, 96, 161, 232, 7, 64, 116, 169, 113, 214, 66, 81, 27, 217, 57, 216, 224, 2, 130, 231, 241, 91, 110, 2, 17, 0, 0, 0, 4, 57, 225, 213, 211, 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