Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bd3a05071a1dda65ac2f84e44f93d7d3e0b7a71d619cd1da8ec792d2cb0f256

Tx prefix hash: 77ee820551bdd4e5566835bc8a5e4d7f95ab25f206fb45e853560bf5874fe624
Tx public key: 2a5d4030e193885c9afc87f0a8c50d0aa7016e47960e0fa80409c9362b788926
Timestamp: 1715141555 Timestamp [UCT]: 2024-05-08 04:12:35 Age [y:d:h:m:s]: 00:190:04:37:37
Block: 1017282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136133 RingCT/type: yes/0
Extra: 012a5d4030e193885c9afc87f0a8c50d0aa7016e47960e0fa80409c9362b7889260211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ebc0aa793297810d0557135b22a15fd3f62e9c38e232e82a46670d34391b018 0.600000000000 1481053 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": 1017292, "vin": [ { "gen": { "height": 1017282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ebc0aa793297810d0557135b22a15fd3f62e9c38e232e82a46670d34391b018" } } ], "extra": [ 1, 42, 93, 64, 48, 225, 147, 136, 92, 154, 252, 135, 240, 168, 197, 13, 10, 167, 1, 110, 71, 150, 14, 15, 168, 4, 9, 201, 54, 43, 120, 137, 38, 2, 17, 0, 0, 0, 5, 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