Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f806fc6803f11899d738ccb15a0262cfcdb74f1f6dc631f291786dde437a48a9

Tx prefix hash: 9123880d2c15c34121e1edf54e2d25510ccc0a5bfa53990cbcb5cf184882a2bd
Tx public key: f76fd6e78f788893eccd25a126b6f0c1f14aad3cbbfa7d9570fed1729e3a3eb2
Timestamp: 1702492564 Timestamp [UCT]: 2023-12-13 18:36:04 Age [y:d:h:m:s]: 01:102:05:35:08
Block: 912405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334198 RingCT/type: yes/0
Extra: 01f76fd6e78f788893eccd25a126b6f0c1f14aad3cbbfa7d9570fed1729e3a3eb202110000000d33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc4c93d155f36d73b2bbc6709537d3993b2e87c2eaa1d28b2188fca4110314ce 0.600000000000 1369633 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": 912415, "vin": [ { "gen": { "height": 912405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc4c93d155f36d73b2bbc6709537d3993b2e87c2eaa1d28b2188fca4110314ce" } } ], "extra": [ 1, 247, 111, 214, 231, 143, 120, 136, 147, 236, 205, 37, 161, 38, 182, 240, 193, 241, 74, 173, 60, 187, 250, 125, 149, 112, 254, 209, 114, 158, 58, 62, 178, 2, 17, 0, 0, 0, 13, 51, 175, 153, 244, 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