Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d0f189ef0928f780d5d59f2e5d4a30aca80e4c3b3fec0f1cd48f2183a0ffbdc

Tx prefix hash: 1e6a0135c744c9084ec275775197b93d5776db2dca94f5042520e566f60eeed1
Tx public key: 75837cc117b03627d3b1148f40cdfb4b080ef69f5c4772ca451bac6117aa7aa6
Timestamp: 1721038708 Timestamp [UCT]: 2024-07-15 10:18:28 Age [y:d:h:m:s]: 01:116:17:34:39
Block: 1066177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341931 RingCT/type: yes/0
Extra: 0175837cc117b03627d3b1148f40cdfb4b080ef69f5c4772ca451bac6117aa7aa602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9be19a496516b243c84be3ebf15a2cac301a668be1ca4065f5413e36f48db7e 0.600000000000 1536750 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": 1066187, "vin": [ { "gen": { "height": 1066177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9be19a496516b243c84be3ebf15a2cac301a668be1ca4065f5413e36f48db7e" } } ], "extra": [ 1, 117, 131, 124, 193, 23, 176, 54, 39, 211, 177, 20, 143, 64, 205, 251, 75, 8, 14, 246, 159, 92, 71, 114, 202, 69, 27, 172, 97, 23, 170, 122, 166, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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