Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa2cfef40d1077f34e5baa08241c104961cf9acf501820caaebed29f6e510c1f

Tx prefix hash: 2d68d2e8710f10b3ab6cd205fa4e150fd1c8479c6d1769f404227630e95565ef
Tx public key: 28803a9261c1211762f93c3628128629f2bcac4616f3d1eed47b9a1f21ad5327
Timestamp: 1703524933 Timestamp [UCT]: 2023-12-25 17:22:13 Age [y:d:h:m:s]: 01:317:01:44:57
Block: 920970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485432 RingCT/type: yes/0
Extra: 0128803a9261c1211762f93c3628128629f2bcac4616f3d1eed47b9a1f21ad532702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa9d360a948d987681255f87b1ea1d26926a48f0ef0ffb6a70c4f7147d072ddb 0.600000000000 1378654 of 15

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": 920980, "vin": [ { "gen": { "height": 920970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa9d360a948d987681255f87b1ea1d26926a48f0ef0ffb6a70c4f7147d072ddb" } } ], "extra": [ 1, 40, 128, 58, 146, 97, 193, 33, 23, 98, 249, 60, 54, 40, 18, 134, 41, 242, 188, 172, 70, 22, 243, 209, 238, 212, 123, 154, 31, 33, 173, 83, 39, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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