Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765c410d10d09bdefd4c0c0987784374718cbf9c132ca7ee3b9a7cfb96017237

Tx prefix hash: 63280b4012c564a0c8b9f733279b21744fec8f1e0cbfca5d4a8be11a09472d0e
Tx public key: 5cfbb7dfcea996628ec89c71f060fca5d6ad48b583a853a6f4165a0bff9fff79
Timestamp: 1685315850 Timestamp [UCT]: 2023-05-28 23:17:30 Age [y:d:h:m:s]: 01:357:22:12:22
Block: 770260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517047 RingCT/type: yes/0
Extra: 015cfbb7dfcea996628ec89c71f060fca5d6ad48b583a853a6f4165a0bff9fff79021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.721111646000 dcy

stealth address amount amount idx
00: a4d0a70df8430b56a7a90c55fd0eefd9a133a0b1b07de6eafd8bfe655ec2b612 1.721111646000 1219559 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": 770270, "vin": [ { "gen": { "height": 770260 } } ], "vout": [ { "amount": 1721111646, "target": { "key": "a4d0a70df8430b56a7a90c55fd0eefd9a133a0b1b07de6eafd8bfe655ec2b612" } } ], "extra": [ 1, 92, 251, 183, 223, 206, 169, 150, 98, 142, 200, 156, 113, 240, 96, 252, 165, 214, 173, 72, 181, 131, 168, 83, 166, 244, 22, 90, 11, 255, 159, 255, 121, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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