Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14321f7821810496006f4d7700cdc2d0f1f6a8f8f68d1f7b1d04542273685a3a

Tx prefix hash: 4798b3ed8442fb4efbd13dc85a4aba52948bae6e0b2e04d3287c04e91f99d55a
Tx public key: 39f544e50d43bca4161919314fa9f8cc3b6e75ae41e5d235ceeb27ca61b90821
Timestamp: 1718269725 Timestamp [UCT]: 2024-06-13 09:08:45 Age [y:d:h:m:s]: 00:361:15:53:09
Block: 1043218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258491 RingCT/type: yes/0
Extra: 0139f544e50d43bca4161919314fa9f8cc3b6e75ae41e5d235ceeb27ca61b908210211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfa8bfb58ea5aaa4150aa0751817159fdf2d53a8d6d39086294342bdc0936870 0.600000000000 1512315 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": 1043228, "vin": [ { "gen": { "height": 1043218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfa8bfb58ea5aaa4150aa0751817159fdf2d53a8d6d39086294342bdc0936870" } } ], "extra": [ 1, 57, 245, 68, 229, 13, 67, 188, 164, 22, 25, 25, 49, 79, 169, 248, 204, 59, 110, 117, 174, 65, 229, 210, 53, 206, 235, 39, 202, 97, 185, 8, 33, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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