Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 286a53d1ef16223cc2897e973864fb383ea157b4af0862e6f258239cf77019b3

Tx prefix hash: e63d947211ddc6b5f95a6180a2233d4468de34a9447804b4faafdb0ae1ce9ce3
Tx public key: 884db295bd965a23c9a39a6da9f82f986c44cc8d857ccd971938e1f2efddac64
Timestamp: 1704145503 Timestamp [UCT]: 2024-01-01 21:45:03 Age [y:d:h:m:s]: 01:316:15:58:14
Block: 926107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485156 RingCT/type: yes/0
Extra: 01884db295bd965a23c9a39a6da9f82f986c44cc8d857ccd971938e1f2efddac640211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84c9f7514f66a1a7155e1c3ddc63a65e545c62e43dc99e0acd342bdee6c6633c 0.600000000000 1383881 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": 926117, "vin": [ { "gen": { "height": 926107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c9f7514f66a1a7155e1c3ddc63a65e545c62e43dc99e0acd342bdee6c6633c" } } ], "extra": [ 1, 136, 77, 178, 149, 189, 150, 90, 35, 201, 163, 154, 109, 169, 248, 47, 152, 108, 68, 204, 141, 133, 124, 205, 151, 25, 56, 225, 242, 239, 221, 172, 100, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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