Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26e5cfd16fb2b7c904a66ffaba847779d71cb108a42d217d76d52cd0ed8f97c2

Tx prefix hash: fe2789c048258fb13351ad9926d1fde78521b4efe71b0d3f4fc1f29a82532a18
Tx public key: 63e924b500e8e55123866d14463645520b536ff1d992cea6b8c425b6e978d0cb
Timestamp: 1723428862 Timestamp [UCT]: 2024-08-12 02:14:22 Age [y:d:h:m:s]: 00:244:11:42:06
Block: 1085978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174626 RingCT/type: yes/0
Extra: 0163e924b500e8e55123866d14463645520b536ff1d992cea6b8c425b6e978d0cb02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4588b4231503e04fdc385e47f99e00b2c7f32a36e99fe41192f29703799131a4 0.600000000000 1560569 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": 1085988, "vin": [ { "gen": { "height": 1085978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4588b4231503e04fdc385e47f99e00b2c7f32a36e99fe41192f29703799131a4" } } ], "extra": [ 1, 99, 233, 36, 181, 0, 232, 229, 81, 35, 134, 109, 20, 70, 54, 69, 82, 11, 83, 111, 241, 217, 146, 206, 166, 184, 196, 37, 182, 233, 120, 208, 203, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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