Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7a0f71bebc6dac37ca44fb9bdd0dbbca22a58a061afab157f7d974d1aaf903d

Tx prefix hash: cd3c60c5a5de2a0faa4a6524163c07d9fa606748598011f1f13dbf530c8348af
Tx public key: 77fec700e9dbed1e53d9e82a6e754fa73644a94f371257202727c25f8b2e7c70
Timestamp: 1723513266 Timestamp [UCT]: 2024-08-13 01:41:06 Age [y:d:h:m:s]: 00:216:09:15:21
Block: 1086681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154546 RingCT/type: yes/0
Extra: 0177fec700e9dbed1e53d9e82a6e754fa73644a94f371257202727c25f8b2e7c70021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6934e715d256e3360405f4372f7d4de0887fdf7087880b6b0b4e99a0bde84b08 0.600000000000 1561280 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": 1086691, "vin": [ { "gen": { "height": 1086681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6934e715d256e3360405f4372f7d4de0887fdf7087880b6b0b4e99a0bde84b08" } } ], "extra": [ 1, 119, 254, 199, 0, 233, 219, 237, 30, 83, 217, 232, 42, 110, 117, 79, 167, 54, 68, 169, 79, 55, 18, 87, 32, 39, 39, 194, 95, 139, 46, 124, 112, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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