Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0390bb30e84eb6caa792fa74576a845f79dfc51a784a6b3feb12513037fec1

Tx prefix hash: df007f36fa8cb5f54b296126181b2b3e68d053409c729e0bb2db11ae2c1c834d
Tx public key: a73d65ab752de614cc5e8642b5918c3944f8b8fba3f1eba10411448ef5c9618c
Timestamp: 1577795565 Timestamp [UCT]: 2019-12-31 12:32:45 Age [y:d:h:m:s]: 04:322:03:17:02
Block: 35724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119321 RingCT/type: yes/0
Extra: 01a73d65ab752de614cc5e8642b5918c3944f8b8fba3f1eba10411448ef5c9618c021100000003d81c26c0000000000000000000

1 output(s) for total of 467.339416692000 dcy

stealth address amount amount idx
00: a3eafa041f028348f12e56a853a805e94b8212a64be9c5c2ef161d9d5d612f32 467.339416692000 60329 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": 35734, "vin": [ { "gen": { "height": 35724 } } ], "vout": [ { "amount": 467339416692, "target": { "key": "a3eafa041f028348f12e56a853a805e94b8212a64be9c5c2ef161d9d5d612f32" } } ], "extra": [ 1, 167, 61, 101, 171, 117, 45, 230, 20, 204, 94, 134, 66, 181, 145, 140, 57, 68, 248, 184, 251, 163, 241, 235, 161, 4, 17, 68, 142, 245, 201, 97, 140, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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