Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbbef8623726db535b1747d38aa05afef2e85da2977f63578812163d5978177c

Tx prefix hash: e2f25b7dae74a2224defc158e59a02d49df325949995f779d1cc7c76b8bc8130
Tx public key: 421ca86d7c5b6ceac2f36d682e0ffc4e6c4bc2a1b4eb016626ca33d6dd5de88f
Timestamp: 1661154070 Timestamp [UCT]: 2022-08-22 07:41:10 Age [y:d:h:m:s]: 02:149:18:16:30
Block: 571231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 628477 RingCT/type: yes/0
Extra: 01421ca86d7c5b6ceac2f36d682e0ffc4e6c4bc2a1b4eb016626ca33d6dd5de88f02110000003075e3f0e9000000000000000000

1 output(s) for total of 7.857324128000 dcy

stealth address amount amount idx
00: c2d9a3d1418b1bfdfa1189c1090fab599b820fc83148ae431c19df80d8a5e527 7.857324128000 1004433 of 0

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": 571241, "vin": [ { "gen": { "height": 571231 } } ], "vout": [ { "amount": 7857324128, "target": { "key": "c2d9a3d1418b1bfdfa1189c1090fab599b820fc83148ae431c19df80d8a5e527" } } ], "extra": [ 1, 66, 28, 168, 109, 124, 91, 108, 234, 194, 243, 109, 104, 46, 15, 252, 78, 108, 75, 194, 161, 180, 235, 1, 102, 38, 202, 51, 214, 221, 93, 232, 143, 2, 17, 0, 0, 0, 48, 117, 227, 240, 233, 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