Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b526ee4a512a295028e2c9bd08f2bcb1133024fc70f23ccbe61b141be41a84e

Tx prefix hash: 44c5af46f26badcf1145455b643a0a36e10f9b686b3cdb244a082f92d01889c5
Tx public key: 7d06a1e89a22ea5bb816e169a3daf0b265b1b8b1e1fe2d40fb1e5682fb45e87c
Timestamp: 1574743041 Timestamp [UCT]: 2019-11-26 04:37:21 Age [y:d:h:m:s]: 05:075:04:40:33
Block: 17648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196338 RingCT/type: yes/0
Extra: 017d06a1e89a22ea5bb816e169a3daf0b265b1b8b1e1fe2d40fb1e5682fb45e87c0211000000015ce78bfa000000000000000000

1 output(s) for total of 536.445652797000 dcy

stealth address amount amount idx
00: 2b28dddeb456bf4c1ab5d405eef5efa68c70b06e309aba945981e94b7b7bcbc8 536.445652797000 25943 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": 17658, "vin": [ { "gen": { "height": 17648 } } ], "vout": [ { "amount": 536445652797, "target": { "key": "2b28dddeb456bf4c1ab5d405eef5efa68c70b06e309aba945981e94b7b7bcbc8" } } ], "extra": [ 1, 125, 6, 161, 232, 154, 34, 234, 91, 184, 22, 225, 105, 163, 218, 240, 178, 101, 177, 184, 177, 225, 254, 45, 64, 251, 30, 86, 130, 251, 69, 232, 124, 2, 17, 0, 0, 0, 1, 92, 231, 139, 250, 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