Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0e87a029bb9ca6dbf8398a1ed9ac5abb0476e4749abc40379a190729875e677

Tx prefix hash: 36b3f5433ec7302328408e20425037bd4e6d6608b35fbc2bf9bc06dac7c0ed0e
Tx public key: e9f7af7f019bc267747b5da7dafe45ee21267e0dd5d97d1d994525a95562e84e
Timestamp: 1705845431 Timestamp [UCT]: 2024-01-21 13:57:11 Age [y:d:h:m:s]: 01:128:13:58:50
Block: 940171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353053 RingCT/type: yes/0
Extra: 01e9f7af7f019bc267747b5da7dafe45ee21267e0dd5d97d1d994525a95562e84e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8de49b8af835a447bdf7981f53bf2cacb9df48fae270fb1eca0a63d78932136 0.600000000000 1398305 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": 940181, "vin": [ { "gen": { "height": 940171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8de49b8af835a447bdf7981f53bf2cacb9df48fae270fb1eca0a63d78932136" } } ], "extra": [ 1, 233, 247, 175, 127, 1, 155, 194, 103, 116, 123, 93, 167, 218, 254, 69, 238, 33, 38, 126, 13, 213, 217, 125, 29, 153, 69, 37, 169, 85, 98, 232, 78, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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