Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1149e1edad5fe2f2b235a95b6e0c631d1f509d304b5dc1fd469a6017672f21

Tx prefix hash: 80f7091a5cd96e958a7ec68339162af71598a56ac422fee256511513dbbc0f5d
Tx public key: 9b1b4cd3d5d5070c3daf201406cfa30f4397a9f9ed602e2e3a01240dab503870
Timestamp: 1720547861 Timestamp [UCT]: 2024-07-09 17:57:41 Age [y:d:h:m:s]: 00:277:01:37:24
Block: 1062105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197950 RingCT/type: yes/0
Extra: 019b1b4cd3d5d5070c3daf201406cfa30f4397a9f9ed602e2e3a01240dab50387002110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 929a5c66edeb11147a561e705984dc0635c8bbeb3af844f8c746db46a892a3fd 0.600000000000 1532606 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": 1062115, "vin": [ { "gen": { "height": 1062105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "929a5c66edeb11147a561e705984dc0635c8bbeb3af844f8c746db46a892a3fd" } } ], "extra": [ 1, 155, 27, 76, 211, 213, 213, 7, 12, 61, 175, 32, 20, 6, 207, 163, 15, 67, 151, 169, 249, 237, 96, 46, 46, 58, 1, 36, 13, 171, 80, 56, 112, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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