Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27f6c27ab56d86c11e297eb98f43af773bd2a3b8fba4ce097543f67917544b26

Tx prefix hash: 19e6303ca482c83b418dfb57719deea188f3fa3b2d30b69fe2f5cd94536f52df
Tx public key: 7c8b143f055e316d3b1c9261e3181a6e6b44db9bc76a11a9a40a15496c14f662
Timestamp: 1583753180 Timestamp [UCT]: 2020-03-09 11:26:20 Age [y:d:h:m:s]: 04:121:18:29:09
Block: 79419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 981601 RingCT/type: yes/0
Extra: 017c8b143f055e316d3b1c9261e3181a6e6b44db9bc76a11a9a40a15496c14f662021100000001995a6b02000000000000000000

1 output(s) for total of 334.851828967000 dcy

stealth address amount amount idx
00: a1e5a9b9263a1b841e6373f573fa4a3e29941a65ecb4fb5f1eff2a31c0eedd7f 334.851828967000 145255 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": 79429, "vin": [ { "gen": { "height": 79419 } } ], "vout": [ { "amount": 334851828967, "target": { "key": "a1e5a9b9263a1b841e6373f573fa4a3e29941a65ecb4fb5f1eff2a31c0eedd7f" } } ], "extra": [ 1, 124, 139, 20, 63, 5, 94, 49, 109, 59, 28, 146, 97, 227, 24, 26, 110, 107, 68, 219, 155, 199, 106, 17, 169, 164, 10, 21, 73, 108, 20, 246, 98, 2, 17, 0, 0, 0, 1, 153, 90, 107, 2, 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