Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf7da90b9407c58e40981d95e68512d7db6c411fbd30ab5b2a4695a12ab938aa

Tx prefix hash: 7bef0f0b334fd07b74ca47e29162b599d8e6c6c8542cc11a20226f6f891c660c
Tx public key: 9fce4e1f36479bbdf5e1a191c00bbb787daa1e76c53a1a587a8f5380e88b4b10
Timestamp: 1719200219 Timestamp [UCT]: 2024-06-24 03:36:59 Age [y:d:h:m:s]: 00:292:21:46:01
Block: 1050916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209305 RingCT/type: yes/0
Extra: 019fce4e1f36479bbdf5e1a191c00bbb787daa1e76c53a1a587a8f5380e88b4b1002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42a8200d5d811448f18c6a0458438dfe4ff0ff6aa7401714c1d33c43afab6615 0.600000000000 1521093 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": 1050926, "vin": [ { "gen": { "height": 1050916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42a8200d5d811448f18c6a0458438dfe4ff0ff6aa7401714c1d33c43afab6615" } } ], "extra": [ 1, 159, 206, 78, 31, 54, 71, 155, 189, 245, 225, 161, 145, 192, 11, 187, 120, 125, 170, 30, 118, 197, 58, 26, 88, 122, 143, 83, 128, 232, 139, 75, 16, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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