Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652d5da0abe3600ac2ca137c99c5577929848c467519b9b88161f3ccc5229094

Tx prefix hash: f7cbc9042f30443a9b40d9e8d038a13c5e8e8bf1aa14274a3f47551444c4ef62
Tx public key: 5b4c8ec65140e04a856824a8d2df101a4b08f56ebd49681cd05698b040ec48a3
Timestamp: 1727011384 Timestamp [UCT]: 2024-09-22 13:23:04 Age [y:d:h:m:s]: 00:111:06:18:18
Block: 1115686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79543 RingCT/type: yes/0
Extra: 015b4c8ec65140e04a856824a8d2df101a4b08f56ebd49681cd05698b040ec48a302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b903acf16d57310d938a8093ad67585b2c1e2c6d626c1ea657001ff09f4df26e 0.600000000000 1595903 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": 1115696, "vin": [ { "gen": { "height": 1115686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b903acf16d57310d938a8093ad67585b2c1e2c6d626c1ea657001ff09f4df26e" } } ], "extra": [ 1, 91, 76, 142, 198, 81, 64, 224, 74, 133, 104, 36, 168, 210, 223, 16, 26, 75, 8, 245, 110, 189, 73, 104, 28, 208, 86, 152, 176, 64, 236, 72, 163, 2, 17, 0, 0, 0, 12, 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