Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e1f9fe47862c71b8bc4cfaa284ba07d89135b3436efbdf6b3ca460a13b47c3e

Tx prefix hash: 9d91e04ae4bb6cf42ae735e54c9a8ff3319c6874309ade6b0c03e9cabf7df432
Tx public key: cc3b61830414c92c15847f4c17dc69429af48b512d54a44fe7799c59e9a4af85
Timestamp: 1579012385 Timestamp [UCT]: 2020-01-14 14:33:05 Age [y:d:h:m:s]: 05:050:17:02:16
Block: 45347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186458 RingCT/type: yes/0
Extra: 01cc3b61830414c92c15847f4c17dc69429af48b512d54a44fe7799c59e9a4af850211000000af391a8d0e000000000000000000

1 output(s) for total of 434.257576535000 dcy

stealth address amount amount idx
00: 9b06a001eab5eb8fe6f19c35def365b3f80da7cc94d1b861bb2d9ad224662c10 434.257576535000 82823 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": 45357, "vin": [ { "gen": { "height": 45347 } } ], "vout": [ { "amount": 434257576535, "target": { "key": "9b06a001eab5eb8fe6f19c35def365b3f80da7cc94d1b861bb2d9ad224662c10" } } ], "extra": [ 1, 204, 59, 97, 131, 4, 20, 201, 44, 21, 132, 127, 76, 23, 220, 105, 66, 154, 244, 139, 81, 45, 84, 164, 79, 231, 121, 156, 89, 233, 164, 175, 133, 2, 17, 0, 0, 0, 175, 57, 26, 141, 14, 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