Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4923a2d7c5f072d03af4031bfa428a9a79628dd60ee49f563b60137fbdc389ba

Tx prefix hash: 27cbabfdd6d660b6020c5762e8e481fee82228fdad16aaabf4ecf90e24605cf0
Tx public key: 2ff8e3e34a20a2920e7c8a57cf26d0993640a8e140f193e8b4a368ef90f73057
Timestamp: 1711493247 Timestamp [UCT]: 2024-03-26 22:47:27 Age [y:d:h:m:s]: 01:072:21:11:21
Block: 987053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313083 RingCT/type: yes/0
Extra: 012ff8e3e34a20a2920e7c8a57cf26d0993640a8e140f193e8b4a368ef90f7305702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b6bf0e884452f69eb9ec7cfea7f72e79714c9e32c56d2a74cec1275029c58ba 0.600000000000 1447294 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": 987063, "vin": [ { "gen": { "height": 987053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b6bf0e884452f69eb9ec7cfea7f72e79714c9e32c56d2a74cec1275029c58ba" } } ], "extra": [ 1, 47, 248, 227, 227, 74, 32, 162, 146, 14, 124, 138, 87, 207, 38, 208, 153, 54, 64, 168, 225, 64, 241, 147, 232, 180, 163, 104, 239, 144, 247, 48, 87, 2, 17, 0, 0, 0, 3, 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