Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba8b0f347497dc1e6662259bcb01868d4f34e557cd2bc454a5580c1fb136b9f5

Tx prefix hash: 99d29a41f890a8c5f8b30ee0e28312f9f628492f99e51bcfa9fe63baeb5b809e
Tx public key: 5271754db110bacc047b73d8385122c8b68daaa699feb4565b6abccffa3b952c
Timestamp: 1718305303 Timestamp [UCT]: 2024-06-13 19:01:43 Age [y:d:h:m:s]: 00:224:08:19:31
Block: 1043504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160500 RingCT/type: yes/0
Extra: 015271754db110bacc047b73d8385122c8b68daaa699feb4565b6abccffa3b952c0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74042ce0a468d60ef67ff7dc8b2b2e8cdefe7b5c0847eb481d1724471a6836f2 0.600000000000 1512657 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": 1043514, "vin": [ { "gen": { "height": 1043504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74042ce0a468d60ef67ff7dc8b2b2e8cdefe7b5c0847eb481d1724471a6836f2" } } ], "extra": [ 1, 82, 113, 117, 77, 177, 16, 186, 204, 4, 123, 115, 216, 56, 81, 34, 200, 182, 141, 170, 166, 153, 254, 180, 86, 91, 106, 188, 207, 250, 59, 149, 44, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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