Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d50c109c2eb4105a16e2e8f57c55c658c8720d2e53d39a303c04c1348f357689

Tx prefix hash: b8f8a4e9212bb0555c0c9cb27160b771f879dd38cadc9c380c7a9674890209a3
Tx public key: ab2eb04ccfa9014c4fcfdc9b9a8d1a818dd5454dda092aaef4a55e1cf2273e35
Timestamp: 1685463836 Timestamp [UCT]: 2023-05-30 16:23:56 Age [y:d:h:m:s]: 01:275:03:16:44
Block: 771484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457812 RingCT/type: yes/0
Extra: 01ab2eb04ccfa9014c4fcfdc9b9a8d1a818dd5454dda092aaef4a55e1cf2273e35021100000001b3164c24000000000000000000

1 output(s) for total of 1.705114005000 dcy

stealth address amount amount idx
00: 3468279aa151855549ebb1222606ceddb1820c376b961d169dc5bfdebc4cd3e8 1.705114005000 1220853 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": 771494, "vin": [ { "gen": { "height": 771484 } } ], "vout": [ { "amount": 1705114005, "target": { "key": "3468279aa151855549ebb1222606ceddb1820c376b961d169dc5bfdebc4cd3e8" } } ], "extra": [ 1, 171, 46, 176, 76, 207, 169, 1, 76, 79, 207, 220, 155, 154, 141, 26, 129, 141, 213, 69, 77, 218, 9, 42, 174, 244, 165, 94, 28, 242, 39, 62, 53, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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