Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17ecc0f643984f88e47600804978bf49d97a98f266c2956ae55509fa4ced219f

Tx prefix hash: 0c33b02da85a46d0003e75c8e4ef96e04aa8db8b8b5a698e369d17bee8b456a1
Tx public key: b5e8cecae114aec63caa424a99ee8d89eb36e2dcc4da574a9f5938231e69599f
Timestamp: 1643898288 Timestamp [UCT]: 2022-02-03 14:24:48 Age [y:d:h:m:s]: 03:270:12:36:07
Block: 431393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 970256 RingCT/type: yes/0
Extra: 01b5e8cecae114aec63caa424a99ee8d89eb36e2dcc4da574a9f5938231e69599f021100000002c9067537000000000000000000

1 output(s) for total of 22.835799293000 dcy

stealth address amount amount idx
00: 28a7022d4873f1f0697ef1f87b7dac29aa52ecadbf1e599940200af2d82acad5 22.835799293000 841579 of 0

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": 431403, "vin": [ { "gen": { "height": 431393 } } ], "vout": [ { "amount": 22835799293, "target": { "key": "28a7022d4873f1f0697ef1f87b7dac29aa52ecadbf1e599940200af2d82acad5" } } ], "extra": [ 1, 181, 232, 206, 202, 225, 20, 174, 198, 60, 170, 66, 74, 153, 238, 141, 137, 235, 54, 226, 220, 196, 218, 87, 74, 159, 89, 56, 35, 30, 105, 89, 159, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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