Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee5c71f3bb5b02f3121bad433eb9f213fa81275a23569710130e9f99d33f7040

Tx prefix hash: 68ff9024fb710c550cb32dc08cc98c649cb14ad2879441d892b755b99f8945f4
Tx public key: 91ad90c3aa35f8674917a0fddd8d85f451aa53f32ac33ae45d552e315cb1189d
Timestamp: 1707630955 Timestamp [UCT]: 2024-02-11 05:55:55 Age [y:d:h:m:s]: 01:055:22:37:23
Block: 954997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301024 RingCT/type: yes/0
Extra: 0191ad90c3aa35f8674917a0fddd8d85f451aa53f32ac33ae45d552e315cb1189d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b8b9d104c8e5fcbad4cdd9733188e3b00b50a4c6085fd4acb74b1165d456565 0.600000000000 1414279 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": 955007, "vin": [ { "gen": { "height": 954997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b8b9d104c8e5fcbad4cdd9733188e3b00b50a4c6085fd4acb74b1165d456565" } } ], "extra": [ 1, 145, 173, 144, 195, 170, 53, 248, 103, 73, 23, 160, 253, 221, 141, 133, 244, 81, 170, 83, 243, 42, 195, 58, 228, 93, 85, 46, 49, 92, 177, 24, 157, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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