Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27d6960ea684e64235fd104116714ae1a8aac2b747d57ae886ace1ea10678a43

Tx prefix hash: 83d46a3f48d9d877b87323386d1676376e99f04a1825627a0999d6392e7b5e66
Tx public key: a3e8057d8af132c04ddecafc403b63d62f75aceb2c64a4ab7cecf8293897f49c
Timestamp: 1632171584 Timestamp [UCT]: 2021-09-20 20:59:44 Age [y:d:h:m:s]: 03:097:00:07:16
Block: 337778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845357 RingCT/type: yes/0
Extra: 01a3e8057d8af132c04ddecafc403b63d62f75aceb2c64a4ab7cecf8293897f49c02110000000106faf294000000000000000000

1 output(s) for total of 46.647495437000 dcy

stealth address amount amount idx
00: b1ca9f2dbf8fbe8c6a11bcdc44dedbe03aafd59ec84b5eeb8bc1cea2074b7424 46.647495437000 695409 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": 337788, "vin": [ { "gen": { "height": 337778 } } ], "vout": [ { "amount": 46647495437, "target": { "key": "b1ca9f2dbf8fbe8c6a11bcdc44dedbe03aafd59ec84b5eeb8bc1cea2074b7424" } } ], "extra": [ 1, 163, 232, 5, 125, 138, 241, 50, 192, 77, 222, 202, 252, 64, 59, 99, 214, 47, 117, 172, 235, 44, 100, 164, 171, 124, 236, 248, 41, 56, 151, 244, 156, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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