Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1f8c76ed8f1992a618f02e939b02ea6e06ec35545e6ed87c3639a74865ae35

Tx prefix hash: 7d2bf61d7bfdda509bf7362fd1dcab67c5169f934204b26274e76c7381fa7e21
Tx public key: d0b9de616c1657e97c9c3b10439fee601115bddce3f7905d715a27385b11ad41
Timestamp: 1718114626 Timestamp [UCT]: 2024-06-11 14:03:46 Age [y:d:h:m:s]: 00:291:00:08:04
Block: 1041932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207948 RingCT/type: yes/0
Extra: 01d0b9de616c1657e97c9c3b10439fee601115bddce3f7905d715a27385b11ad41021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90b0f8c9d178ca3e83892aeabdde134c5009ece9ac7f57bf9d047228c8fafb1e 0.600000000000 1510727 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": 1041942, "vin": [ { "gen": { "height": 1041932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90b0f8c9d178ca3e83892aeabdde134c5009ece9ac7f57bf9d047228c8fafb1e" } } ], "extra": [ 1, 208, 185, 222, 97, 108, 22, 87, 233, 124, 156, 59, 16, 67, 159, 238, 96, 17, 21, 189, 220, 227, 247, 144, 93, 113, 90, 39, 56, 91, 17, 173, 65, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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