Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa3166cc88c56b2d8cbb715f48694080d5ddd58f65e65aa1bd152c64951c70a0

Tx prefix hash: 662459247db9336406e43604d2a31ab895e7a958e7e17370188edbaea36d47e8
Tx public key: 5d7fdc739309b08f666250f07848e986af8e584d416f1f5a84c52f83a0cc70e0
Timestamp: 1624273905 Timestamp [UCT]: 2021-06-21 11:11:45 Age [y:d:h:m:s]: 03:257:07:49:42
Block: 281626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 950526 RingCT/type: yes/0
Extra: 015d7fdc739309b08f666250f07848e986af8e584d416f1f5a84c52f83a0cc70e002110000007fd54f680a000000000000000000

1 output(s) for total of 71.590710174000 dcy

stealth address amount amount idx
00: cf6304f81b2a5b0f3c09e4c072d0bb1f1634d4eeda51aa4d909baf370c47dc40 71.590710174000 589833 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": 281636, "vin": [ { "gen": { "height": 281626 } } ], "vout": [ { "amount": 71590710174, "target": { "key": "cf6304f81b2a5b0f3c09e4c072d0bb1f1634d4eeda51aa4d909baf370c47dc40" } } ], "extra": [ 1, 93, 127, 220, 115, 147, 9, 176, 143, 102, 98, 80, 240, 120, 72, 233, 134, 175, 142, 88, 77, 65, 111, 31, 90, 132, 197, 47, 131, 160, 204, 112, 224, 2, 17, 0, 0, 0, 127, 213, 79, 104, 10, 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