Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a91526ed92deca5aef828d73d385a434d7cfcdb6eb17679efcb9d18cfdf7aa97

Tx prefix hash: 322bc0f8dc244294aee7d914b3b288a2b1e423bf98218fd003a669f1d7d8103d
Tx public key: 7ec375aeeec2d94d6765fd3f71d21df855c22d5ede0ecbb16035919108862d31
Timestamp: 1734418531 Timestamp [UCT]: 2024-12-17 06:55:31 Age [y:d:h:m:s]: 00:093:02:14:24
Block: 1177002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66324 RingCT/type: yes/0
Extra: 017ec375aeeec2d94d6765fd3f71d21df855c22d5ede0ecbb16035919108862d3102110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b78990b3593a3df87fbb83511e694fbe55b1cd0028261c8f5317722b94e39a2a 0.600000000000 1663363 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": 1177012, "vin": [ { "gen": { "height": 1177002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b78990b3593a3df87fbb83511e694fbe55b1cd0028261c8f5317722b94e39a2a" } } ], "extra": [ 1, 126, 195, 117, 174, 238, 194, 217, 77, 103, 101, 253, 63, 113, 210, 29, 248, 85, 194, 45, 94, 222, 14, 203, 177, 96, 53, 145, 145, 8, 134, 45, 49, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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