Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97a025f1a1394ddee430818670ef5384c7151a662ccb93d29fd3b171783d9f5d

Tx prefix hash: 88ee9d943d02528d70808c36a87f806dc5079c14dd27936912025850ee33297c
Tx public key: 45713f445c93d84929c11b6c110a541617d4676c3af37ff8377081708eaa4d6e
Timestamp: 1583549166 Timestamp [UCT]: 2020-03-07 02:46:06 Age [y:d:h:m:s]: 04:359:03:30:01
Block: 78057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150843 RingCT/type: yes/0
Extra: 0145713f445c93d84929c11b6c110a541617d4676c3af37ff8377081708eaa4d6e0211000000324943cd9f000000000000000000

1 output(s) for total of 338.349507600000 dcy

stealth address amount amount idx
00: e323e825d469c0232cb75acef9f64b5d56e40e5e570cc5beb35b86ed21ec6143 338.349507600000 143330 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": 78067, "vin": [ { "gen": { "height": 78057 } } ], "vout": [ { "amount": 338349507600, "target": { "key": "e323e825d469c0232cb75acef9f64b5d56e40e5e570cc5beb35b86ed21ec6143" } } ], "extra": [ 1, 69, 113, 63, 68, 92, 147, 216, 73, 41, 193, 27, 108, 17, 10, 84, 22, 23, 212, 103, 108, 58, 243, 127, 248, 55, 112, 129, 112, 142, 170, 77, 110, 2, 17, 0, 0, 0, 50, 73, 67, 205, 159, 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