Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 490be26a851a2c082d6d2538a119875165f0a85090d12c060dc9d091ebf3b92e

Tx prefix hash: bf916670aa7b8d1a4c6f6579851a15a361e0d2985576ad4575e8f78b83ffd4a5
Tx public key: 741439891e58346dc700f8d1581501ed98e38f642a1d2402f85c838c53128e11
Timestamp: 1648171115 Timestamp [UCT]: 2022-03-25 01:18:35 Age [y:d:h:m:s]: 02:277:15:11:32
Block: 465770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 717922 RingCT/type: yes/0
Extra: 01741439891e58346dc700f8d1581501ed98e38f642a1d2402f85c838c53128e1102110000000c4a0f5013000000000000000000

1 output(s) for total of 17.567537746000 dcy

stealth address amount amount idx
00: 8137de93a5df0dcfd1904771dfb045d6ab167bd214b2980e8667010a9b8579be 17.567537746000 883943 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": 465780, "vin": [ { "gen": { "height": 465770 } } ], "vout": [ { "amount": 17567537746, "target": { "key": "8137de93a5df0dcfd1904771dfb045d6ab167bd214b2980e8667010a9b8579be" } } ], "extra": [ 1, 116, 20, 57, 137, 30, 88, 52, 109, 199, 0, 248, 209, 88, 21, 1, 237, 152, 227, 143, 100, 42, 29, 36, 2, 248, 92, 131, 140, 83, 18, 142, 17, 2, 17, 0, 0, 0, 12, 74, 15, 80, 19, 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