Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ccd112e8ad2b3cea7e98d20133b2099bc93637bdb712541bddb1b0bb3ca72d2

Tx prefix hash: 9db44e8042e05247df74cb45198440dbc6dec8f189d194b6b539fe6f2e433de5
Tx public key: 5ca0ed65e1c668965971ce6fcabbed40c1b3a387d0d1c08e62959da34058a31a
Timestamp: 1580614179 Timestamp [UCT]: 2020-02-02 03:29:39 Age [y:d:h:m:s]: 04:331:16:33:26
Block: 56817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128415 RingCT/type: yes/0
Extra: 015ca0ed65e1c668965971ce6fcabbed40c1b3a387d0d1c08e62959da34058a31a0211000000034ac5aa02000000000000000000

1 output(s) for total of 397.871211323000 dcy

stealth address amount amount idx
00: 3d580aa6bc038760a922d0739b5bf2c3f353a3c57efca6cb92656f478d42667c 397.871211323000 104784 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": 56827, "vin": [ { "gen": { "height": 56817 } } ], "vout": [ { "amount": 397871211323, "target": { "key": "3d580aa6bc038760a922d0739b5bf2c3f353a3c57efca6cb92656f478d42667c" } } ], "extra": [ 1, 92, 160, 237, 101, 225, 198, 104, 150, 89, 113, 206, 111, 202, 187, 237, 64, 193, 179, 163, 135, 208, 209, 192, 142, 98, 149, 157, 163, 64, 88, 163, 26, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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