Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c3e238cf320e0f4ffc8b19644cf2d9a9b8079f2e013a13f6f7eb5e3f89a45ab

Tx prefix hash: cc4239d54ecb7db8194c17cfad80a1895269ef66d6e5b1b1300dfdd80686572c
Tx public key: ebc2c21c9b4d9d4d9ac9dfc851b4545016aac5a7fb7f7cd40631fac0c1de33d2
Timestamp: 1648218350 Timestamp [UCT]: 2022-03-25 14:25:50 Age [y:d:h:m:s]: 02:355:01:11:27
Block: 466124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 773095 RingCT/type: yes/0
Extra: 01ebc2c21c9b4d9d4d9ac9dfc851b4545016aac5a7fb7f7cd40631fac0c1de33d20211000000014da16a3a000000000000000000

1 output(s) for total of 17.520155074000 dcy

stealth address amount amount idx
00: 7e5620b79c2b63bb455cba6fc62f67578921daa50a0c9268920abfc2eb3915a0 17.520155074000 884369 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": 466134, "vin": [ { "gen": { "height": 466124 } } ], "vout": [ { "amount": 17520155074, "target": { "key": "7e5620b79c2b63bb455cba6fc62f67578921daa50a0c9268920abfc2eb3915a0" } } ], "extra": [ 1, 235, 194, 194, 28, 155, 77, 157, 77, 154, 201, 223, 200, 81, 180, 84, 80, 22, 170, 197, 167, 251, 127, 124, 212, 6, 49, 250, 192, 193, 222, 51, 210, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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