Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f88a64eb09db2335de134684c1d64f20c11e6322c5010b7f9b8012e576872e

Tx prefix hash: b3e5d65fb0293f2791cd050ffd3f4fba8a3f759c1ac335d146ebb3ca4c685a7c
Tx public key: 1d2159d8aaf5f621141313e66d41f93ec2851151f3a9c732e2cbc916bdb0c5ef
Timestamp: 1719992218 Timestamp [UCT]: 2024-07-03 07:36:58 Age [y:d:h:m:s]: 00:274:18:12:34
Block: 1057494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196301 RingCT/type: yes/0
Extra: 011d2159d8aaf5f621141313e66d41f93ec2851151f3a9c732e2cbc916bdb0c5ef0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e1f1a6b52d26f6b3386b570e0b4dfa8f3fe7d420b578ba9e97fad49c0d9472f 0.600000000000 1527929 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": 1057504, "vin": [ { "gen": { "height": 1057494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e1f1a6b52d26f6b3386b570e0b4dfa8f3fe7d420b578ba9e97fad49c0d9472f" } } ], "extra": [ 1, 29, 33, 89, 216, 170, 245, 246, 33, 20, 19, 19, 230, 109, 65, 249, 62, 194, 133, 17, 81, 243, 169, 199, 50, 226, 203, 201, 22, 189, 176, 197, 239, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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