Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da26c06633cbb5541460fc8e542a8791c55fcc188fa91c5868c42e90c07d61ae

Tx prefix hash: 289b6d58bb6ee9674fdba583035ea7ca5c70d05ffb1c640fe5a855840c2ce48f
Tx public key: fd41a81c0fb196dd5a739628aa942db299d9e8e6d77652557e18d1ffa6841185
Timestamp: 1609181382 Timestamp [UCT]: 2020-12-28 18:49:42 Age [y:d:h:m:s]: 04:122:00:16:33
Block: 171007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100490 RingCT/type: yes/0
Extra: 01fd41a81c0fb196dd5a739628aa942db299d9e8e6d77652557e18d1ffa68411850211000001134ea414e5000000000000000000

1 output(s) for total of 166.488210353000 dcy

stealth address amount amount idx
00: e30f48fdeccc438409538b8ff159504ff37ddf7d5dbbbe8f32999209c436b09c 166.488210353000 321442 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": 171017, "vin": [ { "gen": { "height": 171007 } } ], "vout": [ { "amount": 166488210353, "target": { "key": "e30f48fdeccc438409538b8ff159504ff37ddf7d5dbbbe8f32999209c436b09c" } } ], "extra": [ 1, 253, 65, 168, 28, 15, 177, 150, 221, 90, 115, 150, 40, 170, 148, 45, 178, 153, 217, 232, 230, 215, 118, 82, 85, 126, 24, 209, 255, 166, 132, 17, 133, 2, 17, 0, 0, 1, 19, 78, 164, 20, 229, 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