Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea016305dbace67a925428c37b99b7aa0be4626a87cda7170cbe8176904ec784

Tx prefix hash: f243ab45bde18c31f8eac67d55d7438ea317deb6a94a72d0a6f8431109299642
Tx public key: a43de5a1ae68e131bbd67fb29543a7fb499dff3bc58d01d9fa0302154632b4b8
Timestamp: 1725130080 Timestamp [UCT]: 2024-08-31 18:48:00 Age [y:d:h:m:s]: 00:229:04:10:41
Block: 1100083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163645 RingCT/type: yes/0
Extra: 01a43de5a1ae68e131bbd67fb29543a7fb499dff3bc58d01d9fa0302154632b4b8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5f580c1f970a583ee8c57fb61800b8743db422d11faf03f2d3e30ec3d2e6f09 0.600000000000 1576056 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": 1100093, "vin": [ { "gen": { "height": 1100083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5f580c1f970a583ee8c57fb61800b8743db422d11faf03f2d3e30ec3d2e6f09" } } ], "extra": [ 1, 164, 61, 229, 161, 174, 104, 225, 49, 187, 214, 127, 178, 149, 67, 167, 251, 73, 157, 255, 59, 197, 141, 1, 217, 250, 3, 2, 21, 70, 50, 180, 184, 2, 17, 0, 0, 0, 3, 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