Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30633ec8eeae96a892e5cd6792c751d13e662e6f2593368a580f81d94c207334

Tx prefix hash: f6a8dd75eb2185cbfcd24606ca40ca848f226b0f9b19bb43ec759913edb1ebe3
Tx public key: 779e1487d2285d051148ea77e6d393e968349666bf4e6e15a3e4e3afa07e1dd0
Timestamp: 1713545061 Timestamp [UCT]: 2024-04-19 16:44:21 Age [y:d:h:m:s]: 01:015:19:30:53
Block: 1004030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272263 RingCT/type: yes/0
Extra: 01779e1487d2285d051148ea77e6d393e968349666bf4e6e15a3e4e3afa07e1dd00211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f0cfa0b68772d1ea445a678954765fad72bf18e8a9666681dc55a5a7b9e05b7 0.600000000000 1464592 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": 1004040, "vin": [ { "gen": { "height": 1004030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f0cfa0b68772d1ea445a678954765fad72bf18e8a9666681dc55a5a7b9e05b7" } } ], "extra": [ 1, 119, 158, 20, 135, 210, 40, 93, 5, 17, 72, 234, 119, 230, 211, 147, 233, 104, 52, 150, 102, 191, 78, 110, 21, 163, 228, 227, 175, 160, 126, 29, 208, 2, 17, 0, 0, 0, 7, 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