Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5515a13fb85891496bcf8d4c5309069c247cbfbaf7fdb8118c888ca4521be7d3

Tx prefix hash: bdf169b074e10b3d84e5f5f354b812f803263bf93c8aee0df28c8a2189803896
Tx public key: a8afa612165c7cfeabd51ec3359f31b2eef13633d72a475aaf3fbae5f9530575
Timestamp: 1698076414 Timestamp [UCT]: 2023-10-23 15:53:34 Age [y:d:h:m:s]: 01:146:17:05:24
Block: 876000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365870 RingCT/type: yes/0
Extra: 01a8afa612165c7cfeabd51ec3359f31b2eef13633d72a475aaf3fbae5f953057502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.768154137000 dcy

stealth address amount amount idx
00: 3963fac71e44d0ce8d3010f045f06db6fe2d104d92ce157576f17aab258bfc47 0.768154137000 1331308 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": 876010, "vin": [ { "gen": { "height": 876000 } } ], "vout": [ { "amount": 768154137, "target": { "key": "3963fac71e44d0ce8d3010f045f06db6fe2d104d92ce157576f17aab258bfc47" } } ], "extra": [ 1, 168, 175, 166, 18, 22, 92, 124, 254, 171, 213, 30, 195, 53, 159, 49, 178, 238, 241, 54, 51, 215, 42, 71, 90, 175, 63, 186, 229, 249, 83, 5, 117, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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