Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cad53c11360feaac4b5faf7351bed3e6799f18fa35860e5e7bdb7c0a4407d7f

Tx prefix hash: b3ea0e8e22ba88247dda41cc28900d463a5564fb797fe07c5c2257699098e9e7
Tx public key: 552372d1e5d75a7e33dce378a887bac6f2426838542349e77e3d1be5bb326245
Timestamp: 1621845663 Timestamp [UCT]: 2021-05-24 08:41:03 Age [y:d:h:m:s]: 04:161:14:21:41
Block: 266040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136203 RingCT/type: yes/0
Extra: 01552372d1e5d75a7e33dce378a887bac6f2426838542349e77e3d1be5bb3262450211000000d185d8f8f2000000000000000000

1 output(s) for total of 80.630542361000 dcy

stealth address amount amount idx
00: 157b35f0721d3ab50787cfb0d706c528afc00e182686f8026d7f91490f3e7e8b 80.630542361000 559088 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": 266050, "vin": [ { "gen": { "height": 266040 } } ], "vout": [ { "amount": 80630542361, "target": { "key": "157b35f0721d3ab50787cfb0d706c528afc00e182686f8026d7f91490f3e7e8b" } } ], "extra": [ 1, 85, 35, 114, 209, 229, 215, 90, 126, 51, 220, 227, 120, 168, 135, 186, 198, 242, 66, 104, 56, 84, 35, 73, 231, 126, 61, 27, 229, 187, 50, 98, 69, 2, 17, 0, 0, 0, 209, 133, 216, 248, 242, 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